This page defines users and roles involved in CloudSocket. It heavily references the different types of process models used by the suite.

Business Process Designer #

The Business Process Designer creates Business Process Models (Level-I processes) using the CloudSocket Design tool. The processes reference an Ontology provided by an Ontology provider. In practice, the Business Process Designer may be a Business Consultant or a CloudSocket Broker.

Executable Process Designer #

The Executable Process Desiger creates an Executable Business Process (Level-II process) based on a Business Process Model; mapping tasks to a workflow of service invocations. In practice, the Executable Business Designer may be a 'Technical' Consultant, a service provider, or a CloudSocket broker.

Deployable Process Modeller #

The Deployable Process Modeller builds a BPaaS Cloudlet based on an Executable Business Process (Level-III process); mapping references to service types to service instances offered by service providers. In practice, the Executable Business Designer may be a 'Technical' Consultant, a service provider, or a CloudSocket broker.

CloudSocket Broker

The main task of the broker besides the fact that it can be contributing to defining the various models is that it selects deployable (Level-III processes) and offeres them to its users (Business Process Users). Hence, it takes a Level-III process and renders it to something executable using a BPaaS provider.

Business Process User\\ #

User of CloudSocket in the sense that it unlocks a Business Process for a dedicated group of end users (the tenant).

End User

The actual person/set of persons interacting with the Business Process realised through the Cloudlet, e.g. a case worker in a personnal department. Very likely that this person belongs to the same institution as the operator.

BPaaS Provider

Offers one or multiple business processes to Business Process Users. Runs these under its own control either using own hardware or further P/IaaS offerings.

External Service Provider

Organization installing, executing and managing a service instance that Level-III processes can be bound to. Also, the External Service Provider autonomously defines SLAs for the Service and is responsible to fulfill such SLA. He is paid according to the usage of the Service he provides.